Most Powerful Open Source ERP

Developer Documentation

Guideline Use Base_view Prefix Followed By Business Filed and FieldLibrary For Field Library Title

For naming consistency.

Guideline Proxy Fields Should Share Semantics

To keep consistency across fields.

Guideline Only Use Proxy Fields In Non Field Library Forms

To prevent excessive customisation.

Guideline Technical Template Fields Are Defined In Base_viewFieldLibrary

Non semantic fields should not be duplicated.

Guideline Field Library Fields Should Be Semantically Unified

Use consistent naming patterns.

Guideline Business Library Fields Proxy From Core Fields

Use three levels: core, business, custom

Guideline A Proxy Field Never Links To An External Field Library

Business templates must work standalone.

Guideline Use Glossary Defined Prefix For Specific Semantics

Field libraries should be consistent within.

Guideline A Form Field Proxies From A Buiness Template Field

Differentiate Core, Business and Custom Fields.

Guideline Semantic Field Is Named Using My Prefix, Technical Context And Semantic Name

Differentiate between semantic and technical template fields.

Guideline Use My Prefix and Class Name For Template Field Name

To prevent creating multiple technical template fields.

Guideline A Business Template Has Only One Field Library

Field libraries share semantic configuration.

Guideline Semantic Field Should Be Used In Favor Of Technical Field

Semantic fields are more specific and descriptive.

ERP5 Technical Note Steps To Create Field Libraries

Outline of the four steps to follow when creating field libraries.